Skip to content

Conversation

@brendan-kellam
Copy link
Contributor

@brendan-kellam brendan-kellam commented Jan 17, 2026

Upgrade Node.js to v22 LTS and enable HTTP proxy support via environment variables.

This resolves the fetch failed error when Sourcebot attempts to access external services like GitLab through an HTTP/HTTPS proxy, as Node.js v22+ is required for automatic proxy detection using HTTP_PROXY, HTTPS_PROXY, and NO_PROXY.

Fixes #751

Summary by CodeRabbit

  • New Features

    • Added HTTP proxy configuration support via environment variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY, NODE_USE_ENV_PROXY).
  • Documentation

    • Added HTTP Proxy Configuration section documenting all proxy-related environment variables and their usage.
  • Chores

    • Updated base container images to latest compatible versions.

✏️ Tip: You can customize this high-level summary in your review settings.

- Upgrade base Node.js image from v20 to v22-alpine3.20
- Upgrade Alpine from 3.19 to 3.20 for both Node and Go base images
- Add NODE_USE_ENV_PROXY=1 environment variable to enable automatic proxy configuration
- Document HTTP proxy environment variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY)

This enables Sourcebot to work in enterprise environments that require HTTP/HTTPS proxies for external access. Node.js v22 natively supports proxy configuration via environment variables when NODE_USE_ENV_PROXY is enabled.

Co-authored-by: brendan <[email protected]>
@cursor
Copy link

cursor bot commented Jan 17, 2026

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@coderabbitai
Copy link

coderabbitai bot commented Jan 17, 2026

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

This pull request implements HTTP proxy configuration support by upgrading Docker base images to versions supporting Node.js proxy environment variables (node:22 and alpine3.20), enabling the NODE_USE_ENV_PROXY flag in the runner stage, and documenting the HTTP_PROXY, HTTPS_PROXY, NO_PROXY, and NODE_USE_ENV_PROXY environment variables.

Changes

Cohort / File(s) Summary
Docker Infrastructure
Dockerfile
Updated Node.js base image from v20 to v22 and Alpine from 3.19 to 3.20; added NODE_USE_ENV_PROXY=1 environment variable to enable proxy support in runner stage
Configuration Documentation
docs/docs/configuration/environment-variables.mdx
Added HTTP Proxy Configuration section documenting HTTP_PROXY, HTTPS_PROXY, NO_PROXY, and NODE_USE_ENV_PROXY variables with defaults and usage descriptions

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main changes: upgrading Node version (from v20 to v22) and adding HTTP proxy configuration support.
Linked Issues check ✅ Passed The PR fully addresses issue #751 by upgrading to Node v22, enabling NODE_USE_ENV_PROXY, and documenting HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables.
Out of Scope Changes check ✅ Passed All changes are directly scoped to the linked issue: base image upgrades to v22, NODE_USE_ENV_PROXY enablement, and proxy configuration documentation are all required for issue #751.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@brendan-kellam brendan-kellam changed the title HTTP proxy configuration chore: Upgrade node version & add HTTP proxy configuration Jan 19, 2026
@brendan-kellam brendan-kellam marked this pull request as ready for review January 19, 2026 23:28
@github-actions

This comment has been minimized.

@brendan-kellam
Copy link
Contributor Author

@coderabbitai review

@coderabbitai
Copy link

coderabbitai bot commented Jan 19, 2026

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@Dockerfile`:
- Around line 18-19: Update the Node.js base image in the Dockerfile by
replacing the FROM line that currently reads "FROM node:22-alpine3.20" with a
tag that includes Node v22.21.0 or later (e.g., "FROM node:22.21.0-alpine3.20"
or a newer patch), so the NODE_USE_ENV_PROXY feature is available; leave the
golang FROM ("FROM golang:1.23.4-alpine3.20") unchanged.

In `@docs/docs/configuration/environment-variables.mdx`:
- Around line 40-47: The Markdown table under "HTTP Proxy Configuration" uses
double-leading pipes which breaks rendering; update the table by replacing the
leading "||" with a single "|" on every table line (header, separator, and data
rows) so standard Markdown table syntax is used, keeping the existing column
headings and cell content (e.g., variable names like HTTP_PROXY, HTTPS_PROXY,
NO_PROXY, NODE_USE_ENV_PROXY) unchanged.

@brendan-kellam brendan-kellam merged commit 11f69d6 into main Jan 20, 2026
9 checks passed
@brendan-kellam brendan-kellam deleted the cursor/SOU-226-http-proxy-configuration-2375 branch January 20, 2026 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FR] HTTP Proxy Configuration

3 participants